Software Vault: The Gold Collection/Software Vault - The Gold Collection (American Databankers) (1993).ISO/cdr11/adde13a.zip/BACKBONE.HOW

Text File | 1993-06-26 | 9KB | 151 lines

                               March 17, 1993

                             Changed procedures
                                 to get an
                 ECHOMAIL CONFERENCE ADDED TO THE BACKBONE

In an effort to make adding a conference to the backbone both easier
and more clear, the following procedures are established.  These
modify slightly the procedures listed in BOP 1.03.

To add a new conference to backbone distribution the following steps
must be followed.

        I.  The moderator of the conference must either place a
        message in the ZEC conference addressed to Backbone or send a
        netmail to the ZEC who will put the needed message into the
        ZEC conference.

            a.  Please note any netmail requests other than to the ZEC
            will be ignored. Only messages in the ZEC conference will
            be considered to be valid requests in Region 13.

            b.  The message must include either the appropriate line
            from your areas.bbs or a list of fidonet addresses that
            currently receive the conference.  (If a list of nodes is
            included it would be more accurate to gather this from
            originating messages in the conference than from $eenbys
            or path lines). This demonstrates wide spread interest in
            the conference and its current distribution.

            c.  The rest of the message should just be a request to
            have the message added to backbone distribution. (A sample
            message follows).

        II. At the same time the request message is posted, a copy of
        the Elist confirmation message (less password) should also be
        posted.  If the conference has been in the Elist for some time
        and the listing is current, then just post the Elist section
        that covers the conference.  (In other words cut and paste a
        message made up of the ELlist confirmation). If the conference
        is not currently Elisted or if a confirmation message has not
        been received, DO NOT post a request message.

Any request message that does not have the required Elist message as
outlined above will not be considered a valid request and will be
ignored.

        III. Two RECs also must request that the conference be added.
        Those requests will also be posted in the ZEC conference.
        Please note -- the request to the RECs MUST come from NECs
        within their regions who are asking to have the conference
        added to the backbone.  Those requests to the REC must be
        placed in a regional sysop echo.  Most RECs require that
        requests come from at least two different nets. Moderators
        please DO NOT send messages to the RECs as they will probably
        be ignored.

Echos not attaining backbone status within one month of their listing
will be dropped.  Upon expiration of the request without the echo
attaining backbone status, the moderator may request that an echo be
listed an additional 4 weeks.

Please direct questions to Dan Buda in the ZEC echo.

Once the above requirements have been met the conference will be added
with the next Fidonet.NA.  A REC will monitor the ZEC conference and
track all messages addressed to Backbone.  That REC will maintain
Fidostat.NA tracking the requirements for each requested conference.
John Souvestre (396/1) will hatch both out Fidostat.NA and Fidonet.NA
each weekend to the RHubs.

        Sample ZEC echo request message:

     To:  BACKBONE

             Please consider this a request to add MULT-SCLEROSIS to
     the backbone for distribution.

             Current known distribution.

     C:\ECHO\MULT_S       MULT-SCLEROSIS 1:108/50 125/15 141/420
                          150/140 157/512 243/23 260/225 279/14
                          320/101 363/15 3603/110 101/460 2220/10
                          2:252/200

             Elist confirmation message.

      Date:   Wed Jan 29 1992  00:00:38
      From:   EchoList of 1:1/201
      To:     ZEC
      Subj:   Mod Update ACCEPTED for Edition 202.
      Attr:   privileged recvd
      netmail

      > TAG   MULT-SCLEROSIS
      > TITL  Multiple Sclerosis
      > DESC  By request of a local support group at one of the
      > DESC  hospitals, this Electronic Support Group is now
      > DESC  being formed.  As the name implies, it is a
      > DESC  support group for MS.
      > MOD
      > TOT
      > VOL
      > REST
      > DIST
      > GATE
      > SEEN
      > PATH

     Area MULT-SCLEROSIS Updated.

      --- ELi8tUpd 2.2.2


        Sample ELIST echo request message:


     To:  ECHOLIST    at:  1:1/201
     Subject:  MOD UPD

     The body of the message would contain:

     TAG   NJ-SHORE
     TITL  New Jersey Shore Topics
     DESC  A general chatter conference for Jersey Shore residents
     DESC  and those interested in Jersey Shore events, activities and
     DESC  chit-chat.
     MOD   Mike Fuchs, 1:266/71
     PASS  paranoia
     TOT   3
     VOL   5/week
     DIST  LOCAL-NJSHORE
     SEEN 1:266/71 107/412 416 7:520/1024
     PATH 1:266/71 412
     PATH 266/71 416 7:520/1024
     ---

     Mike Fuchs, 1:266/71

      This "signature" is unnecessary and ignored, but since the From:
      will probably be Robot or Sysop, it's a nice touch.  Make SURE
      there is a "tear line" (three dashes) after the submission lines
      and before any trailing messages or signature lines.

      Make sure the netmail message is addressed to ECHOLIST at
      1:1/201, and that the subject line is Moderator Update.